Quick question, should I be incrementing the version number (maybe like 2.3.11)? The Arch repos have the build from March 28th.

@vinnyperella I am not against bumping version number, but the software has become mature so no new features are being added recently, so I am not sure whether bumping version is beneficial or causes confusion to all downstream packagers.

I remember that ArchLinux bumps the pkgrel number after “-” for dependency-triggered rebuilds. Are they bumping the pkgrel numbers this time or not?

By the way, thank you for doing the chores!

Strange. The Docker build job returned a 500 error from GitHub.

https://github.com/m13253/dns-over-https/actions/runs/19480485056/job/55751052613#step:5:1

Is GitHub also impacted by today’s Cloudflare outage? (I don’t think GitHub is using Cloudflare, are they?)

@vinnyperella I am not against bumping version number, but the software has become mature so no new features are being added recently, so I am not sure whether bumping version is beneficial or causes confusion to all downstream packagers.

I remember that ArchLinux bumps the pkgrel number after “-” for dependency-triggered rebuilds. Are they bumping the pkgrel numbers this time or not?

By the way, thank you for doing the chores!

Yeah I agree and no it doesn't appear they're bumping the number after the "-" it's still "2.3.10-1" from March 28th 2025. Maybe I'll contact the maintainer as it's listed in the package info and see what's up. And no problem at all I use the client and server a lot and I enjoy making sure things are updated.

Strange. The Docker build job returned a 500 error from GitHub.

https://github.com/m13253/dns-over-https/actions/runs/19480485056/job/55751052613#step:5:1

Is GitHub also impacted by today’s Cloudflare outage? (I don’t think GitHub is using Cloudflare, are they?)

I checked the logs for some reason the URL is not correct when it tries to clone the repo.

92.90 fatal: unable to access 'https://github.com/***/dns-over-https.git/': The requested URL returned error: 500

Looking in to see what the problem is I didn't change anything related to this.

Can you rerun the checks by chance?

@m13253 looks like there may have been an issue with github actions around the time the checks were being run specifically for git operations which is what appears to have failed from the logs.

https://www.githubstatus.com/